River monitoring from satellite radar altimetry in the Zambezi River basin

Satellite radar altimetry can be used to monitor surface water levels from space. While current and past altimetry missions were designed to study oceans, retracking the waveforms returned over land allows data to be retrieved for smaller water bodies or narrow rivers. The objective of this study is the assessment of the potential for river monitoring from radar altimetry in terms of water level and discharge in the Zambezi River basin. Retracked Envisat altimetry data were extracted over the Zambezi River basin using a detailed river mask based on Landsat imagery. This allowed for stage measurements to be obtained for rivers down to 80m wide with an RMSE relative to in situ levels of 0.32 to 0.72m at different locations. The altimetric levels were then converted to discharge using three different methods adapted to different data-availability scenarios: first with an in situ rating curve available, secondly with one simultaneous field measurement of cross-section and discharge, and finally with only historical discharge data available. For the two locations at which all three methods could be applied, the accuracies of the different methods were found to be comparable, with RMSE values ranging from 4.1 to 6.5% of the mean annual in situ gauged amplitude for the first method and from 6.9 to 13.8% for the second and third methods. The precision obtained with the different methods was analyzed by running Monte Carlo simulations and also showed comparable values for the three approaches with standard deviations found between 5.7 and 7.2% of the mean annual in situ gauged amplitude for the first method and from 8.7 to 13.0% for the second and third methods

Draft Genome Sequences of Four Saccharibacter sp. Strains Isolated from Native Bees.

The genus Saccharibacter is currently understudied, with only one described species, Saccharibacter floricola, isolated from a flower. In an effort to better understand the microbes that come in contact with native bee pollinators, we isolated and sequenced four additional strains of Saccharibacter from native bees in the genera Melissodes and Anthophora These genomes range in size from 2,104,494 to 2,316,791 bp (mean, 2,246,664 bp) and contain between 1,860 and 2,167 (mean, 2,060) protein-coding genes

Putting Integrated Systems Health Management Capabilities to Work: Development of an Advanced Caution and Warning System for Next-Generation Crewed Spacecraft Missions

Integrated System Health Management (ISHM) technologies have advanced to the point where they can provide significant automated assistance with real-time fault detection, diagnosis, guided troubleshooting, and failure consequence assessment. To exploit these capabilities in actual operational environments, however, ISHM information must be integrated into operational concepts and associated information displays in ways that enable human operators to process and understand the ISHM system information rapidly and effectively. In this paper, we explore these design issues in the context of an advanced caution and warning system (ACAWS) for next-generation crewed spacecraft missions. User interface concepts for depicting failure diagnoses, failure effects, redundancy loss, "what-if" failure analysis scenarios, and resolution of ambiguity groups are discussed and illustrated

UAS Service Supplier Specification

Within the Unmanned Aircraft Systems (UAS) Traffic Management (UTM) system, the UAS Service Supplier (USS) is a key component. The USS serves several functions. At a high level, those include the following: Bridging communication between UAS Operators and Flight Information Management System (FIMS) Supporting planning of UAS operations Assisting strategic deconfliction of the UTM airspace Providing information support to UAS Operators during operations Helping UAS Operators meet their formal requirements This document provides the minimum set of requirements for a USS. In order to be recognized as a USS within UTM, successful demonstration of satisfying the requirements described herein will be a prerequisite. To ensure various desired qualities (security, fairness, availability, efficiency, maintainability, etc.), this specification relies on references to existing public specifications whenever possible

Differences in level of confidence in diabetes care between different groups of trainees: the TOPDOC diabetes study

Background There is an increasing prevalence of diabetes. Doctors in training, irrespective of specialty, will have patients with diabetes under their care. The aim of this further evaluation of the TOPDOC Diabetes Study data was to identify if there was any variation in confidence in managing diabetes depending on the geographical location of trainees and career aspirations. Methods An online national survey using a pre-validated questionnaire was administered to trainee doctors. A 4-point confidence rating scale was used to rate confidence in managing aspects of diabetes care and a 6-point scale used to quantify how often trainees would contribute to the management of patients with diabetes. Responses were grouped depending on which UK country trainees were based and their intended career choice. Results Trainees in Northern Ireland reported being less confident in IGT diagnosis, use of IV insulin and peri-operative management and were less likely to adjust oral treatment, contact specialist, educate lifestyle, and optimise treatment. Trainees in Scotland were less likely to contact a specialist, but more likely to educate on lifestyle, change insulin, and offer follow-up advice. In Northern Ireland, Undergraduate (UG) and Postgraduate (PG) training in diagnosis was felt less adequate, PG training in emergencies less adequate, and reporting of need for further training higher. Trainees in Wales felt UG training to be inadequate. In Scotland more trainees felt UG training in diagnosis and optimising treatment was inadequate. Physicians were more likely to report confidence in managing patients with diabetes and to engage in different aspects of diabetes care. Aspiring physicians were less likely to feel the need for more training in diabetes care; however a clear majority still felt they needed more training in all aspects of care. Conclusions Doctors in training have poor confidence levels dealing with diabetes related care issues. Although there is variability between different groups of trainees according to geographical location and career aspirations, this is a UK wide issue. There should be a UK wide standardised approach to improving training for junior doctors in diabetes care with local training guided by specific needs.</p

UTM Data Working Group Demonstration 1: Final Report

This document summarizes activities defining and executing the first demonstration of the NASA-FAA Research Transition Team (RTT) Data Exchange and Information Architecture (DEIA) working group (DWG). The demonstration focused on testing the interactions between two key components in the future UAS Traffic Management (UTM) System through a collaborative and distributed simulation of key scenarios. The summary incorporates written feedback from each of the participants in the demonstration. In addition to reporting the activities, this report also provides some insight into future steps of this working group

Closing the Gap in High-Risk Pregnancy Care Using Machine Learning and Human-AI Collaboration

Health insurers often use algorithms to identify members who would benefit from care and condition management programs, which provide personalized, high-touch clinical support. Timely, accurate, and seamless integration between algorithmic identification and clinical intervention depends on effective collaboration between the system designers and nurse care managers. We focus on a high-risk pregnancy (HRP) program designed to reduce the likelihood of adverse prenatal, perinatal, and postnatal events and describe how we overcome three challenges of HRP programs as articulated by nurse care managers; (1) early detection of pregnancy, (2) accurate identification of impactable high-risk members, and (3) provision of explainable indicators to supplement predictions. We propose a novel algorithm for pregnancy identification that identifies pregnancies 57 days earlier than previous code-based models in a retrospective study. We then build a model to predict impactable pregnancy complications that achieves an AUROC of 0.760. Models for pregnancy identification and complications are then integrated into a proposed user interface. In a set of user studies, we collected quantitative and qualitative feedback from nurses on the utility of the predictions combined with clinical information driving the predictions on triaging members for the HRP program

UTM UAS Service Supplier Development: Sprint 2 Toward Technical Capability Level 4

NASA's UAS Traffic Management (UTM) Project has been tasked with developing concepts and initial implementations for integrating and managing small unmanned aircraft systems (UAS) into the low altitude airspace. To accomplish this task, the UTM Project planned a phased approach based on four Technical Capability Levels (TCLs). As of this writing, TCL4 is currently in development for a late Spring 2019 flight demonstration. This TCL is focused on operations in an urban environment and includes the handling of high density environments, large-scale off-nominal conditions, vehicle-to-vehicle communications, detect-and-avoid technologies, communication requirements, public safety operations, airspace restrictions, and other related goals. Through research and testing to date, NASA has developed an architecture for UTM that depends on commercial entities collaboratively providing services that are traditionally provided by the Air Navigation Service Provider (ANSP) in manned aviation. A key component of this architecture is the UAS Service Supplier (USS), which acts as a communications bridge between UAS operators and the ANSP when necessary. In addition, the collection of USSs form a USS Network to collaboratively manage the airspace through the sharing of data and the adherence to a standard or set of standards required to participate in this USS Network. This document provides a record of the second of four planned steps in the development of interoperable USSs that will ultimately support TCL4 flight testing and formalization of the overall UTM concept. To develop these USSs and their underlying specifications, NASA has planned a series of "Sprints" to work with industry partners in implementing the features and develop proposed specifications for USSs in order to to participate in TCL4. This report describes Sprint Two. In this Sprint, there was a major theme with four goals. The theme was the development and testing of a new USS discovery system, to better enable USSs to find and communicate with each other. The goals supporting this theme were: participants needed to implement and exercise the discovery service for USS-USS communications; USSs needed to demonstrate strategic deconfliction through operation sharing; the systems were to use discovery to aid in handling off-nominal operations; and finally, there was an investigation of an initial off-nominal reporting capability

UTM UAS Serivce Supplier Development: Sprint 1 Toward Technical Capability Level 4

NASA's UAS Traffic Management (UTM) Project has been tasked with developing concepts and initial implementations for integrating and managing small unmanned aircraft systems (UAS) into the low altitude airspace. To accomplish this task, the Project planned a phased approach based on four Technical Capability Levels (TCLs). As of this writing, TCL4 is currently in development for a late Spring 2019 flight demonstration. This TCL is focused on operations in an urban environment and includes the handling of high density and large-scale off-nominal conditions, vehicle-to-vehicle communications, detect-and-avoid technologies, communication requirements, public safety operations, airspace restrictions, and other related goals. Through research and testing to date, NASA has developed an architecture for UTM that depends on commercial entities collaboratively providing services that are traditionally provided by the Air Navigation Service Provider(ANSP) in manned aviation. A key component of this architecture is the UAS Service Supplier (USS), which acts as a communications bridge between UAS operators and the ANSP when necessary. In addition, the collection of USSs form a USS Network to collaboratively manage the airspace through the sharing of data and the adherence to a standard or set of standards required to participate in this USS Network. This document provides a record of the first step in the development of interoperable USSs that will ultimately support TCL4 flight testing and formalization of the overall UTM concept. To develop these USSs and the underlying specifications for them, NASA has planned a series of "Sprints" to work with industry partners in implementing the features and proposed specifications for USSs to participate in TCL4. This report describes Sprint One. In this Sprint, the focus was on establishing a baseline for the Application Programming Interfaces (APIs) and their associated data models. In addition, the concept of UAS Volume Reservations (UVR) (areas that impose restrictions on sUAS that are allowed to operate) was tested. NASA provided the specifications and iterated on them with partners while implementers developed to those specifications. NASA then tested each partner's implementation to ensure compatibility with all other implementers. This process helped all stakeholders gain confidence that the foundation for future Sprints was solid